I used Hyper-V in the past to run the Windows Phone emulator on my Win8.1 Pro-running computer, but I had disabled it (as in disabled the feature) because it conflicted with VMWare. Now I need to run the emulator again, but after re-enabling Hyper-V, every time I try to start a VM I get the infamous "something something cannot begin because the hypervisor is not running".

I've gone and looked through many forums posts and tried many things, but to no avail. Here's some stuff that I've tried:

• Completely uninstalling VMWare
• Disabling the Hyper-V feature and re-enabling it between cold boots
• Going into my BIOS and turning on and off virtualization between cold boots
• Making sure DEP is turned on (hardware-wise as well)
• bcdedit /set hypervisorlaunchtype auto
  

Here are some of the readouts given by programs that I've seen recommended for troubleshooting this problem:

> systeminfo.exe

Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

> CoreInfo.exe

Coreinfo v3.21 - Dump information on system CPU and memory topology
Copyright (C) 2008-2013 Mark Russinovich
Sysinternals - www.sysinternals.com

Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
HYPERVISOR      -       Hypervisor is present
VMX             *       Supports Intel hardware-assisted virtualization
EPT             *       Supports Intel extended page tables (SLAT)

> wmic OS Get DataExecutionPrevention_Available
DataExecutionPrevention_Available
TRUE

> wmic OS Get DataExecutionPrevention_Drivers
DataExecutionPrevention_Drivers
TRUE

> bcdedit /enum

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 8.1
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {945303b9-466f-11e3-9a3b-c5a07e9d086f}
integrityservices       Enable
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {1235a14d-466d-11e3-9a3b-c5a07e9d086f}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Here are some images too, showing that my machine is SLAT capable as well as having hardware-enabled DEP: http://imgur.com/a/FTMmy

I've also gone through the event viewer, but I've seen nothing that grabs my attention.

Any ideas? This would bother me less if I hadn't been able to get this working in the past with zero problems whatsoever. And I know that between the time it had worked and now, I have not had any hardware changes, as well as any major driver updates.

Thanks.

• Edited by yet2bedefined 11 hours 13 minutes ago

Install the Hyper-V feature once again and have a look in the multiple Hyper-V logs in Event Log (Applications and Services log > Microsoft > Windows) and see if we can get some more detailed info on what is preventing your VMs from starting.

Thanks for the reply, as well as directing me as where to look in the Event Viewer, I wasn't entirely sure where to look before.

Most of the messages there are from back when Hyper-V worked for me. However, in the Hyper-V-VMMS>Admin category, I see events that correspond with me trying to get things to work. I see "The virtualization infrastructure driver (VID) is not running." popping up every time I start up Windows. Could this be the problem?

The rest of the error/warning logs in that category are just the messages saying that "so-and-so emulator cannot be started because the hypervisor isn't running", or that I'm turning off my computer.

Seems a Intel video driver could be causing problems, if that has been updated since when Hyper-V was working, try rolling back that driver.

Also, is the VID.sys driver existing at all if you look in "Msinfo32.exe" under Software Environment > System Drivers? What is the status of Hyper V Virtualization Infrastructure Driver as found in Device Manager > System devices?

VID.sys and the Hyper-V Virtualizaton driver are both present and operating fine accordinging to Msinfo32 and the device manager, respectively.

I'll try updating/rolling back Intel's video driver, thanks.

OK, updating my Intel video driver to the latest version didn't affect anything, and neither did rolling it back to a version from before I had any problems. The hypervisor still isn't starting up, and the Event Viewer is still logging the same error messages.